home *** CD-ROM | disk | FTP | other *** search
- Path: comma.rhein.de!serpens!not-for-mail
- From: mlelstv@serpens.rhein.de (Michael van Elst)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Messages vs. Semaphores for external clocking
- Date: 10 Apr 1996 11:20:43 +0200
- Organization: dis-
- Message-ID: <4kfuhb$ahh@serpens.rhein.de>
- References: <4ju349$r1e@sparky.navsea.navy.mil> <4jvrqs$hk0@btmpjg.god.bel.alcatel.be> <heinz.17rm@hwg.muc.de> <4kfmes$lle@btmpjg.god.bel.alcatel.be>
- NNTP-Posting-Host: serpens.rhein.de
-
- barnhoorn@nlev00 () writes:
-
- >.not so obviously. When you have two tasks, and one of them is
- >collecting data from some source, and the other one needs this data
- >with regular intervals, I don't see a more easier way to do this
- >then by using global data and disable/enable multitasking.
-
- The trick is to disable multitasking only when necessary and only
- for the tasks that are involved.
-
- >It is
- >a very multitasking-friendly solution,
-
- No. You stop all other tasks (and with Disable() you even stop
- interrupts which is nonsense). With a semaphore you would stop
- only the other task. With message passing you wouldn't stop
- any task at all.
-
- --
- Michael van Elst
-
- Internet: mlelstv@serpens.rhein.de
- "A potential Snark may lurk in every tree."
-